Unique Chain 1.14 #1096
Open
Unique Chain 1.14 #1096
+16,515
−29,870
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BuddyGlas
added
CI-xcm
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Much-anticipated update of Unique to Polkadot 1.14.
This update has been prepared through the joint efforts of @fairax, @BuddyGlas, myself, and @mrshiposha.
In this update
Despite the release of version 1.16.1, we decided to keep the SDK version at 1.14 as it has already been tested and works great.
Regarding the previous PR #1091, I have restructured the commit history and corrected all messages, as well as added the missing changes.
Update note №1
The node in this release with Async Backing performs very poorly. To address this, it was decided to update the node separately to the latest Polkadot SDK to enable Fork Aware Tx Pool in a separate branch. After the new release from Parity, the branches may be merged.
Update note №2
The release has been delayed so much that many outdated branches with intermediate changes have formed during the process. After a successful release, we need to remember to clean up.